🚫 Deprecated: This connector has been deprecated and may be removed in future versions.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | BoxDataConnector |
| Publisher | Box |
| Used in Solutions | Box |
| Collection Method | Azure Function |
| Connector Definition Files | Box_API_FunctionApp.json |
| Ingestion API | HTTP Data Collector API — Azure Function code uses SharedKey/HTTP Data Collector API |
| Custom Log V1 Tables | Yes 🔶 — ingests into tables with type-suffixed columns |
| Microsoft Learn | View on Learn |
The Box data connector provides the capability to ingest Box enterprise's events into Microsoft Sentinel using the Box REST API. Refer to Box documentation for more information.
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
BoxEventsV2_CL |
✓ | ✓ | ✓ |
BoxEvents_CL 🔶 |
✗ | ✓ | ✗ |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
NOTE: This connector uses Azure Functions to connect to the Box REST API to pull logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page for details.
(Optional Step) Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. Follow these instructions to use Azure Key Vault with an Azure Function App.
NOTE: This connector depends on a parser based on Kusto Function to work as expected BoxEvents which is deployed with the Microsoft Sentinel Solution.
STEP 1 - Configuration of the Box events collection
See documentation to setup JWT authentication and obtain JSON file with credentials.
STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function
IMPORTANT: Before deploying the Box data connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Box JSON configuration file, readily available.
WorkspaceIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
PrimaryKeyNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
Option 1 - Azure Resource Manager (ARM) Template
Use this method for automated deployment of the Box data connector using an ARM Tempate.
Click the Deploy to Azure button below.
Select the preferred Subscription, Resource Group and Location.
Enter the AzureSentinelWorkspaceId, AzureSentinelSharedKey, BoxConfigJSON
Mark the checkbox labeled I agree to the terms and conditions stated above.
Click Purchase to deploy.
Option 2 - Manual Deployment of Azure Functions
Use the following step-by-step instructions to deploy the Box data connector manually with Azure Functions (Deployment via Visual Studio Code). Step 1 - Deploy a Function App
1. Download the [Azure Function App](https://aka.ms/sentinel-BoxDataConnector-functionapp) file. Extract archive to your local development computer.
Follow the function app manual deployment instructions to deploy the Azure Functions app using VSCode.
After successful deployment of the function app, follow next steps for configuring it.
Step 2 - Configure the Function App
In the Function App, select the Function App Name and select Configuration.
In the Application settings tab, select + New application setting.
Add each of the following application settings individually, with their respective string values (case-sensitive): AzureSentinelWorkspaceId AzureSentinelSharedKey BOX_CONFIG_JSON logAnalyticsUri (optional)
- Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format:
https://<CustomerId>.ods.opinsights.azure.us.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊